Tree preservation zone

There is a problem

276 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

entity: 19211223

reference: 151
name
tree-preservation-order: undefined
Symonique House and Shenstones Warren Rise New Malden KT3 4SJ
tree-preservation-zone-type: group
geometry: MULTIPOLYGON (((-0.265177 51.414933,-0.265056 51.414700,-0.265026 51.414645,-0.264879 51.414413,-0.264559 51.414450,-0.264322 51.414487,-0.263920 51.414556,-0.263946 51.414579,-0.263997 51.414615,-0.264097 51.414668,-0.264173 51.414700,-0.264204 51.414717,-0.264278 51.414807,-0.264313 51.414856,-0.264587 51.415290,-0.265114 51.415157,-0.265126 51.415118,-0.265136 51.415075,-0.265156 51.415002,-0.265177 51.414933)))
point: POINT (-0.264667 51.414815)
notes
entry-date: 2018-12-18
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

This diagram shows the relationship between the tree preservation order dataset and the tree preservation zone dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree preservation zone dataset.

How to improve Royal Borough of Kingston upon Thames’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL